From: Jonas Dreßler <verdre@v0yd.nl>
Date: Tue, 4 Jun 2019 18:55:29 +0000 (+0200)
Subject: layout: Use addChrome instead of addTopChrome for screenShieldGroup
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~845^2^2~132
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=00f9b7bf69d4f3cfd290953a019a8b9fbf592d15;p=gnome-shell.git

layout: Use addChrome instead of addTopChrome for screenShieldGroup

Make sure the panel is visible above the login and screen shield actors
by adding the screenShieldGroup to the uiGroup underneath the panelBox.

This fixes a regression introduced with 2bd80579eddba9804871ce6c8de742bdf9b1d800

Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1330

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/571
---

diff --git a/js/ui/layout.js b/js/ui/layout.js
index 90385e82c..538c24e73 100644
--- a/js/ui/layout.js
+++ b/js/ui/layout.js
@@ -239,7 +239,7 @@ var LayoutManager = GObject.registerClass({
                                                  clip_to_allocation: true,
                                                  layout_manager: new Clutter.BinLayout(),
                                                });
-        this.addTopChrome(this.screenShieldGroup);
+        this.addChrome(this.screenShieldGroup);
 
         this.panelBox = new St.BoxLayout({ name: 'panelBox',
                                            vertical: true });